Accessing RQM information

woodpryan - Wed Aug 05 11:42:20 EDT 2015

Rolan, you have not given us anywhere near enough information to help you. What, specifically, do you need to do? Have you written any DXL code yet? It may help if you post what you've got already.

ExternalLink el;
Regexp getType = regexp ".*#(.*)";

for el in obj -> "" do {
    string n = name(el);
    string lt = linkType(el);
    string t = "";
    if (getType lt) {
      t = lt[match 1];
    }

    if (t == "validatedBy") display n;
}

Rolan - Wed Aug 05 12:37:24 EDT 2015

Actually I figured out how to get what I needed to show up in a layout DXL column with this code:

ExternalLink el;
Regexp getType = regexp ".*#(.*)";

for el in obj -> "" do {
    string n = name(el);
    string lt = linkType(el);
    string t = "";
    if (getType lt) {
      t = lt[match 1];
    }

    if (t == "validatedBy") display n;
}

Next thing is to figure out how to access more of the RQM test script content from DXL.

 

So far using HttpResponse hr = HttpRequest (HttpGet, body(el), null, null) , then HttpBody hb = hr.body doesn't appear to get any of the content that I would see in the RQM test script if I follow the link from DOORS.

In one module the body text returned ends with "oauth_problem=signature_invalid".  Not sure what needs to done to correct this.

In another module (in another project), the body text actually looks like the body of a web page, but it appears that most of the content is actually generated by javascript, which DOORS doesn't execute.

SudarshanRao - Wed Aug 05 13:52:40 EDT 2015

There's a built-in script to show details of OSLC links in Layout DXL Column - not sure if you've tried it already.
If not, you can try using that to see if that's what you're looking for. Choose to create a new column, select Layout DXL radio button and click on Browse. In the resulting dialog, expand the folder and choose "OSLC - Displays status of QM artifacts linked to objects" and click on OK.

About using http related perms, you can find a sample script in DOORSHOME\lib\dxl\examples\oslc - sample_get.dxl (available only in 9.6 onwards). This should help clarify on what headers are required and how to use the different perms.

signature_invalid indicates problem with configuration (or maybe difference in time between DOORS client and RQM server?). Are you able to create a validated by link?
The other response you get which looks like body of web page, suggests Accept header of the request was not appropriate - should be application/xml or application/rdf+xml.

Hope that helps..

SudarshanRao - Wed Aug 05 13:52:40 EDT 2015

There's a built-in script to show details of OSLC links in Layout DXL Column - not sure if you've tried it already.
If not, you can try using that to see if that's what you're looking for. Choose to create a new column, select Layout DXL radio button and click on Browse. In the resulting dialog, expand the folder and choose "OSLC - Displays status of QM artifacts linked to objects" and click on OK.

About using http related perms, you can find a sample script in DOORSHOME\lib\dxl\examples\oslc - sample_get.dxl (available only in 9.6 onwards). This should help clarify on what headers are required and how to use the different perms.

signature_invalid indicates problem with configuration (or maybe difference in time between DOORS client and RQM server?). Are you able to create a validated by link?
The other response you get which looks like body of web page, suggests Accept header of the request was not appropriate - should be application/xml or application/rdf+xml.

Hope that helps..

SudarshanRao - Wed Aug 05 13:52:40 EDT 2015

There's a built-in script to show details of OSLC links in Layout DXL Column - not sure if you've tried it already.
If not, you can try using that to see if that's what you're looking for. Choose to create a new column, select Layout DXL radio button and click on Browse. In the resulting dialog, expand the folder and choose "OSLC - Displays status of QM artifacts linked to objects" and click on OK.

About using http related perms, you can find a sample script in DOORSHOME\lib\dxl\examples\oslc - sample_get.dxl (available only in 9.6 onwards). This should help clarify on what headers are required and how to use the different perms.

signature_invalid indicates problem with configuration (or maybe difference in time between DOORS client and RQM server?). Are you able to create a validated by link?
The other response you get which looks like body of web page, suggests Accept header of the request was not appropriate - should be application/xml or application/rdf+xml.

Hope that helps..